Using EDI Inbox Processing

1. When you first enter the EDI Inbox Processing, if any transactions have been received into the EDI Inbox, a selection box will appear listing the unprocessed EDI transactions in the EDI Inbox with the following information:

• File name – The file name received from your trading partner(s)
• ID – The trading partner ID
• Partner name – The trading partner name
• UCC Code – The Interchange ID used to identify the trading partner
• Date/Time – The date and time the file was received, if applicable

If no transactions are available, the screen will display the Run Continuously, Process, and Print(X) command options. Transactions can only be processed if they appear in the selection box. If the Home Site ID is invalid, the partner name will display “Invalid Home Site ID”. If the trading partner cannot be found, the partner name will display, “Cannot ID Sender”.

Select one or more transactions to process into the system by scrolling to the transaction and pressing Enter. An asterisk (*) will appear confirming your selection. Or, press F9 to select all transactions. Press F10 when finished.

2. Command options will appear:

• Run Continuously – Select Run Continuously to continually process the incoming EDI Transactions. As transactions are added to the EDI Inbox , the system will process the transactions every 30 seconds. Press the Esc key to exit from Run Continuously.

Note: If the Run Continuously command option is selected, the system will continually poll the EDI Inbox for incoming transactions. This will require the screen to be left open or minimized. Some customers add an extra user license to their system to allow for this unattended "user" to continuously process incoming EDI transactions . This user must be logged out of Net•Yield prior to running Close End of Day.

• Process – Select Process to only process the transaction(s) selected.
• View Errors – Select View Errors to view processing errors. This command option will only be available if processing errors are found. A list of common processing errors can be found below.
• Print(X) – Select Print(X) to print the details of the transactions or choose from a set of other print options. The printout will include the data schema of the transaction, including any error messages that are found. A list of the common processing errors can be found below.

5. A status window displays showing the following information:

• PRTN – The trading partner ID
• EDI File – The trading partner transaction file name
• NY File – The NY file name created
• Start -– The start time for processing the file
• Done – The stop time for processing the file. If an error is encountered in processing the file into the system, it is noted in the last column and an error log is created in the Shared\NetYield\Data\Company Name\EDI Inbox \ Logs folder.

A copy of the processed transaction will be placed in the Shared\NetYield\Data\Company Name\EDI Inbox\History folder. The NY File name is appended to the trading partner file name when the file is copied into the History folder.

6. Once the transactions have been processed into the system, the customer's purchase order can be processed into a sales order or the vendor’s invoice acknowledgement matched to the purchase order in Complete Purchase Orders.

Note: Many type of errors can occur in EDI transactions. The system is designed to only allow properly formatted transactions to be processed in the system. Improperly formatted transactions are flagged so that they may be examined and corrected with the sender. If an error is found, and error log is created and stored in the Log folder within the EDI Inbox folder. The error is shown in the processing windows. An additional View Errors command option will appear so that the error can be viewed. Select the error log file from the selection list that appears. The error log can be displayed in a summary or complete file format from the command options.

Common Processing Errors (see individual transactions for additional error codes)

• UCC Code not found
• DUNS number not found error codes
  • 1 = ISA control problem, or incorrect group count
  • 2 = GS control problem, or incorrect transaction count
  • 3 = ST control problem, or incorrect segment count
  • 4 = unsupported transaction or version
  • 5 = incorrect loop terminator found
  • 6 = undefined transaction segments found
  • 7 = cannot ID transaction type based on info provided
  • 8 = DUNS not found
  • 9 = TI or version does not match site table
    
    

Security Required : System - System Administration